NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
C7000-100NAS randomly drops internet connection
Hello,
My C7000-100NAS modem seems to randomly drop it's Comcast connection. This happen on 2.4 ghz, 5 ghz, and wired connections. There is no pattern, however the dropped connection usually lasts 2-5 minutes. When this happens, using the Netgear Genie is useless, it just stalls when trying to connect. Connecting to the IP of the modem works fine to reach the admin page. When the connection drops, the cable connection report on the C7000-100NAS shows the connection is good, 20x4 bonding. Other times, it reports the connection is offline.
I've been on the phone with Comcast, and they are not seeing anything wrong with the line, and no firmware updates are needed or available.
I see there are many reports of this same behavior with this model. The Amazon page is littered with them. I wish I had seen these reports before buying this pricey peice of equipment. I am hoping Netgear has a resolution. Of course the compimentary support period ended like 10 days ago, which is another source of frustration with this product.
Any help would be appreciated. Thanks.
119 Replies
Please PM me on this topic.
we are aware of some resets done by the ISP for specific customers.
Do you have any information about how to stop these annoying interuptions of interrnet access through the C3700 router/modem? Mine has been doing this and I would like to fix it if possible.
Thank you
Pls post your Event log and power levels form the GUI here. Let me have a look at it.
did you find a solution to the problem...?? Same issue (timing sync failure) . Did reset, comcast checked----only wifi, ethernet works fine....
The C7000 was the problem. Spent a lot of time narrowing down the issue with the help of Comcast. They were very helpful, the tech even gave me his personal cell and helped with some diagnositcs off the clock. I did the typical reset, did not help. Did the factory restore...did not help. The C7000 would actually drop the WAN connection every 20 minutes. Nothing in the logs would indicate trouble, other than the Sync issues I noted earlier. Ruled out every device on the network. My only option was to replace the C7000. Netgear never responded. I will try and return it later this week because its still under warranty. Additional proof that it was the C7000, I replaced it with a Netgear CM1000 and it has been rock solid since minute one...no other changes on the network.
i have the same issue as this guy who started this thread. Did you/he get this fixed, i was on phone for 2 hours today with customer service changed some channels, did some tests, as soon as i hung up, same issues of being dropped from internet, doesnt matter, 5G or ethernet
Since CCutter asked. I never did get this fixed. Netgear was a complete dead end when it came to supporting the C7000. Tried several things and junked it. I did not give up on Netgear. I purchased a Netgear X10 R9000 wireless router and a Netgear Cable Modem CM1000. The combo has been running for well over a year now without any issues. Only down time has been for the necessary firmware updates. The only con is the cost. Of course, having said that it will probably prove me wrong.
I have similar problems with my C7000 and it's now getting to the point where I may have to dump this device. All I want is reliable internet. I've got Time Warner and I don't think the problem is with them. I'm a Network Engineer by trade and by no means does that make me "a "Netgear" expert, it does however mean I possess the ability to troubleshoot further and provide additional information. I've had my fair share of crappy wireless devices along with excellent Enterprise class in Cisco, AeroHive, Juniper, Aruba etc. I'm about to say "to heck with it" and spend $500-1k on an Enterprise device as I've wasted close to that on Linksys and Netgear devices over the years.
The C7000 will randomly drop my internet connection for 60 seconds to 5 minutes. Sometimes, it requires a complete reboot. Sometimes it wakes up from being half dead and I need to do nothing. However, the issues are sporatic but obvious and I would guess Netgear would be fully aware of this bug. One second it will drop ICMP traffic to the internet but the C7000's interface tells me my "Cable Connection" is good and I can ping my LAN interface. Then, it will stop responding to ICMP on it's LAN (internal RFC1918 address) interface but Internet traffic still passes fine. For example, as I'm typing this, I can't ping my LAN interface but I can ping 8.8.8.8 without issue. I just looked again and now my LAN interface responds to ICMP but internet is dead. A few minutes later without doing anything, both start responding. Either way, it's virtually impossible to blame Time Warner for this issue when the local LAN interface won't even respond to ICMP (randomly) and internet traffic responds fine. It's also obviously not a weak wireless signal when I can pass sub 20ms packets to most destinations on the internet but not ping my LAN interface. Bottom line, the C7000 displays such erradic behaviour it doesn't seem stable or this firmware release needs work. Time Warners crappy rented "Technicolor", while having weak wireless signal, is at LEAST reliable.Netgear needs to get on with a stable firmware release or lose customers. Most people don't know how to properly troubleshoot an issue and for costing $200 plus, they shouldn't need to constantly "troubleshoot" what's becoming pretty evident as a firmware issue. Word of mouth spreads and it reflects in reviews.
Word does spread. The Co I work for has stopped recomending Netgear for home offices. That only impacts a dozen or so sales at best, but it's a pea shooter across the bow - lol
Yeah, mine get worse as time goes on. It isn't wireless coverage or signal overlap as I'm a Network Engineer by trade and know how to scan and scope interference issues.
As a good test or temp fix, if you want to see if you're having the same problems as I am (which is likely), when you have wireless related issues: FIRST, disconnect from your 5Ghz network either by disabling/re-enabling wireless or connect to your 2.4Ghz network THEN switch back to 5. Either way, when you disconnect and reconnect from your 5Ghz network, it will (or mine does) connect and work fine for a period of time (10-15 min). Some longer than others. On occassion, I just have to power cycle the C7000 altogether.
I went ahead and took an AeroHive AP which is enterprise class and placed it on a different frequency as the Netgear using the netgear as a local router and the AeroHive as an isolated extension but different network and BAM, the AeroHive works flawlessly as a wireless router while the Netgear (which is in the same room) continues to flake out wirelessly and sometimes as a modem.
It just can't seem to handle any kind of small error correction. Instead, it flakes out for all clients on the 5Ghz network without correcting whatever issue it's having until it reinitiates that connection either by disconnecting the client or restarting the C7000. Pretty bad bug IMO.
I am currently going through a debacle with Time Warner and a C7000 as well.
Unfortunately, I have very little networking expertise. I've honestly never needed any. Everything seemed to be fine and TWC upgraded their system to provide much faster speeds. Immediately I was getting drops, wild speed variations, etc.
Currently I have a connection, but my upstream LED is blinking. I expect to have continued dropping until a tech can come out next week. But, I'm really worried that it's something on my end; namely this C7000.
Here is my log. Any feedback at all will help me tremendously.
Time Priority Description 2016-5-29, 21:32:32 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:51 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:40:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:47:47 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:46 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 1970-1-1, 00:00:56 Warning (5) ToD request sent - No Response received;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:57 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:57 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:32:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:32:53 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 2016-5-29, 22:33:07 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:07 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:33:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:33:22 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 2016-5-29, 22:33:32 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:32 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:35:05 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; Procedure Status Comment Acquire Downstream Channel 729000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only ipv6Only(1) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 15 729000000 Hz -0.1 dBmV 41 dB 0 0 2 Locked QAM256 1 645000000 Hz -0.1 dBmV 39 dB 0 0 3 Locked QAM256 2 651000000 Hz -0.6 dBmV 39 dB 0 0 4 Locked QAM256 3 657000000 Hz -1.3 dBmV 39.6 dB 0 0 5 Locked QAM256 4 663000000 Hz -2.1 dBmV 39.6 dB 0 0 6 Locked QAM256 12 669000000 Hz -1.7 dBmV 39.1 dB 0 0 7 Locked QAM256 5 675000000 Hz -1.9 dBmV 38.5 dB 0 0 8 Locked QAM256 6 681000000 Hz -1.3 dBmV 39.9 dB 0 0 9 Locked QAM256 7 687000000 Hz -0.4 dBmV 40.1 dB 0 0 10 Locked QAM256 8 693000000 Hz -0.3 dBmV 39.9 dB 0 0 11 Locked QAM256 9 699000000 Hz -0.5 dBmV 40.2 dB 0 0 12 Locked QAM256 10 705000000 Hz -0.6 dBmV 40.4 dB 0 0 13 Locked QAM256 11 711000000 Hz -0.9 dBmV 40.4 dB 0 0 14 Locked QAM256 13 717000000 Hz -0.7 dBmV 40.4 dB 0 0 15 Locked QAM256 14 723000000 Hz -0.3 dBmV 40.7 dB 0 0 16 Locked QAM256 16 735000000 Hz 0.3 dBmV 40.5 dB 0 0 17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels (Partial Service) Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 14 5120 Ksym/sec 24200000 Hz 52 dBmV 2 Not Locked Unknown 13 0 Ksym/sec 19400000 Hz 0.0 dBmV 3 Locked ATDMA 15 5120 Ksym/sec 30600000 Hz 51.9 dBmV 4 Locked TDMA 16 2560 Ksym/sec 37000000 Hz 52 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 
Help Center
Show/Hide Help I'm having the same issues with the same model on TWC. They're going to have a tech come in to look at the line and everything, but the signal is within spec. I'm having the SYNC issues in my logs as well.
I'm wondering what other routers to consider that are compatible and comparable in features and power.
Here are my logs: https://dl.dropboxusercontent.com/u/10373192/Screen%20Shot%202016-06-14%20at%209.26.48%20PM.png
https://dl.dropboxusercontent.com/u/10373192/Screen%20Shot%202016-06-14%20at%209.27.05%20PM.png
- Getting the same issues; is there a fix for this now? Does anyone know the latest firmware #
Nothing but crickets from Netgear on the Sync problem
Here is a list of the fimwares based on your ISP
http://kb.netgear.com/app/answers/detail/a_id/25477
Was the tech able to find any issues as I do see some timeouts in your logs that are posted.
DarrenM
- So update. COMCAST came out to check the line and I get 230mbps when I use a cable, on wifi I get 17mbps. Did an online chat with Netgear, no fix. Called and took 45 mins. No fix. Called Best Buy to see if they'll take this rubbish back, nope.
Bottom line, get a new router and forget this company. Need help. The firmware release has not solved the issue with Comcast. We have Comcast Internet only since they started in Illinois area and never had cable TV. Invested in the newer technology because you had a Comcast Certification, so I did not expect these types of issues.
With instructions, we can do and check anything.
Hardware Version
1.05 Mac & Windows Network Firmware Version V1.01.20 Internet only - No Cable - Comcast
Wireless is Itv and Roku
Loosing connections.
These events keep happening over and over again.
Fouter Event Log
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d7:20:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d7:20:80;CMTS-MAC=00:01:5c:7f:9a:5a;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:51 Notice (6) Honoring MDD; IP provisioning mode = IPv6 2016-6-27, 16:15:21 Warning (5) Dynamic Range Window violation 2016-6-29, 09:47:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d7:20:80;CMTS-MAC=00:01:5c:7f:9a:5a;CM-QOS=1.1;CM-VER=3.0; 2016-6-29, 09:47:55 Warning (5) Dynamic Range Window violation 2016-6-29, 13:43:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d7:20:80;CMTS-MAC=00:01:5c:7f:9a:5a;CM-QOS=1.1;CM-VER=3.0;
Frequency start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency Startup Procedure Procedure Status Comment Acquire Downstream Channel 741000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 19 741000000 Hz 3.1 dBmV 39.7 dB 17 71 2 Locked QAM256 1 633000000 Hz 2.3 dBmV 39.7 dB 12 88 3 Locked QAM256 2 639000000 Hz 2.2 dBmV 39.5 dB 21 46 4 Locked QAM256 3 645000000 Hz 2.1 dBmV 39.6 dB 29 115 5 Locked QAM256 4 651000000 Hz 1.8 dBmV 38.7 dB 27 88 6 Locked QAM256 5 657000000 Hz 1.9 dBmV 39.3 dB 18 62 7 Locked QAM256 6 663000000 Hz 2.2 dBmV 39.5 dB 41 56 8 Locked QAM256 7 669000000 Hz 2.5 dBmV 39.6 dB 5 32 9 Locked QAM256 8 675000000 Hz 2.6 dBmV 38.4 dB 29 141 10 Locked QAM256 9 681000000 Hz 2.8 dBmV 39.7 dB 13 59 11 Locked QAM256 10 687000000 Hz 2.9 dBmV 39.7 dB 38 35 12 Locked QAM256 11 693000000 Hz 3 dBmV 39.8 dB 26 59 13 Locked QAM256 12 699000000 Hz 3 dBmV 39.8 dB 23 33 14 Locked QAM256 13 705000000 Hz 2.9 dBmV 39.8 dB 16 54 15 Locked QAM256 14 711000000 Hz 3 dBmV 39.8 dB 10 40 16 Locked QAM256 15 717000000 Hz 2.9 dBmV 39.8 dB 40 28 17 Locked QAM256 16 723000000 Hz 3.4 dBmV 40.4 dB 0 0 18 Locked QAM256 17 729000000 Hz 3.4 dBmV 40.3 dB 0 0 19 Locked QAM256 18 735000000 Hz 3.3 dBmV 40.2 dB 0 0 20 Locked QAM256 20 747000000 Hz 3.6 dBmV 40.3 dB 0 0 21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 81 5120 Ksym/sec 36400000 Hz 45 dBmV 2 Locked ATDMA 82 5120 Ksym/sec 29500000 Hz 44 dBmV 3 Locked ATDMA 83 5120 Ksym/sec 22600000 Hz 42.3 dBmV 4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Current System Time:Wed Jun 29 15:05:57 2016 Additional error just moments ago
2016-6-29, 15:05:51 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE This happened between two other errors dated 2016-06-27
1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT Remember that only iTV and Roku are wireless
Thank you
I too had internet drop issues.
I had very similar power levels to the ones you posted. I see also that you have a ton of uncorrectable errors which was what I had also.
I focused my efforts on eliminating the uncorrectable errors. I read in other places that the ideal downstream power level is 0db and upstream should not be more than 50db. My levels were 4db to 6db downstream and 45db~46db upstream so I decided to try a 3db attenuator. Since I installed the 3db attenuator a few weeks ago I have not seen any unrecoverable errors. My downstream power levels are all below 3db now and my upstream levels are 47db~49db. I bought the 3db attenuator on Amazon for about $9. I will post here again if problems return. If you don't hear from me it means it is still working fine.
One other note, with so many uncorrectable errors you might have physical connection issues. Check all coax connections to make sure they are snug.
Well, I just found out my teenage boys have been reseting the modem on a regular basis.
So my fix was not a fix after all.
Back to debug mode!
I am having the same (or similar) issue. I converted from a Surfboard SB6121/Netgear WNDR4500 combination to a Netgear C70000 modem/router combo less than two months ago. Since then I have constant drops and reconnects. Which wouldn't be that terrible if my virtual desktop (connected by Cisco AnyConnect VPN) refuses to allow tunnel reconnect. So, I have to log all the way back in via an RSA token. At the same time my Cisco IP phone (with built in VPN) drops and has to go through a re-registration process. This really blows because this is my home office. Very often, I will be presenting from my virtual desktop and speaking on my IP phone. Then... I'm gone and have to spend time joining my own webex conference.
My live chat with support was a joke. The rep asked me to go ask IT for the proper VPN settings. I ask to please tell me where I can find the VPN settings on this C7000. Crickets for a few minutes and then I was told there are no VPN settings available for this router - I knew this already. Still, the person said they could not help me unless I got the VPN settings from IT. I told the rep I had a better solution: 1) write off my $214 investment as a lesson learned - never buy Netgear again and 2) throw C7000 in the trash and 3) hook up my old modem and router until I can buy better solution.
I have been having this problem as well recently. At one point i could watch a movie through amazon prime with no problem then all of a sudden i can't through 20 minutes without having to deal with the dropped internet. I really hope this issue can get fixed.
Where are we on this. Any solution yet? At this point I think I might have to go back to use the rent moden from comcast that dealing with this. Does any one know if just using the moden on the c7000 will drop connection 2?
Thanks
Based on experience of myself and others reporting and complaining about the same issue, and similar comments from ISPs, it is unlikely that the problem is a "software issue". Instead, it may well be a combination of a defective component and/or interference on the circuit board level. Since the "problem" experienced with the initial production units can not be resolved by NetGear through software settings or upgrades, it would seem that these units will remain unreliable and can not be "fixed". Since "replacement units" from current production may also have the same manufacturing and/or design defects, that route may not resolve the problem.
Sad that so many people have had this problem with this product. It's fustrating that Netgear thinks they can hide the problem and eveything will be okay. I've related my problems with the C7000-100NAS on several sites hoping to find a solution. As far as I can tell the problem is wider than this 'support' would indicate. The response from Netgear is crickets. The only thing to do is suck it up and buy a different brand modem/router. At least that's what I had to do.
There's an old saying;
Fool me once shame on me
Fool me twice ... well that not going to happen to me with Netgear
I'm having the same issues, I had Comcast out half a dozen times and they have done everything they can to try and fix, when they show up no issies are found, but they have removed splitters, replaced the ends on cables, boosted the signal with an amplifier. Still happens, been happening ever since I bought the modem, now I'm starting to believe it;s the modem not Comcast.
It is not Comcast. C7000, a $220 asset, is in my closet now. I have written it off ass a loss and lesson learned. I almost threw it away or lit it on fire in protest. But, I chose to keep it around as a reminder. I replaced my setup with ASUS gear and all is fine. I have always had Netgear everything. Since their total lack of concern about this known issue I will never buy another. I was recently in the market of a wireless repeater for another location that has a lot of obstruction. Pretty much the only game in town was Netgear. I decided to run ethernet wiring instead.
Trust me. It is the modem/router and they do not care.
If anyone is in doubt, go to dslreports.com/speedtest run the test a few times and click on "see full data in table". You will see that fewer channels are bonding than the modem interface reports.
With the right software you can make anyone see what you want them to see - just ask VW
